Recordation and organization of problem solving data

ABSTRACT

A data model uses a graphical user interface (GUI) for recording and organizing information regarding an object of care. The GUI enables a user to input an observation data set including a plurality of observations, the plurality of observations include at least a first subset of the plurality of observations and a second subset of the plurality of observations. The GUI enables the user to input an action data set including a plurality of actions, the plurality of actions includes at least a first subset of the plurality of actions and a second subset of the plurality of actions. The GUI enables the user to connect a first category of care to at least the first subset of the plurality of observations and at least the first subset of the plurality of actions, and to connect a second category of care to at least the second subset of the plurality of observations and at least the second subset of the plurality of actions, such that each connection indicates a relationship between the respective connected data.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 60/302,120, filed on Jun. 29, 2001, which is hereby incorporated byreference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to storage of information, and more specificallyto a system and method of linking observation data, categories of caredata, and action data.

2. Description of the Related Technology

In most service industry occupations, there is a need for record keepingin order to track the progress of the object of care. For example,doctors keep records concerning each of their patients, mechanics keeprecords of each serviced vehicle, a school administration office maykeep discipline records for each student, and a technical supportdepartment may keep records of each of their callers. These records aregenerally taken in an attempt to allow future readers to quicklyascertain the past history of the specific object of care (object ofcare and object, as used herein, refer generically to the person or itemreceiving the service, such as a patient, client, customer, automobile,student, etc.). In addition, many records attempt to show a connectionbetween observations made regarding the object, a diagnosis of eachcondition, and a history of actions taken in an attempt to remedy eachcondition.

Record keeping has been accomplished in the past using a variety ofdifferent methods. For example, a doctor may use a blank piece of paperto write down his patient observations, diagnosis, and treatments given.This record may then be filed in a patient file until the next patientvisit. When the patient next visits the doctor, there is no orderlymethod of locating observations, diagnosis, and actions taken by thedoctor on prior visits. The doctor typically must skim the prior recordto find the needed information. In addition, it may be difficult, if notimpossible, to determine which observations led to each diagnosis, andwhat actions were taken for each diagnosis. Furthermore, if the doctorwants to add additional observations that relate to a diagnosis given ona prior visit, there is no physical space on the paper and no method ofeasily indicating that the new observations are directly related to theprior diagnosis. This problem becomes more apparent when a patient hasmultiple diagnoses. Similarly, if the doctor wishes to record additionaltreatments given for a prior diagnosis, they are likely listed on thenext available blank line on the paper, which may not be adjacent to theprior diagnosis for which the treatments are prescribed. This may makeit difficult to quickly determine what observations and diagnosis led tothe newly listed treatments. In other words, the reader must decipherwhich findings led the writer to believe specific problems existed andfor which specific problems which actions were taken. Thus, a recordfrom which a reader may easily ascertain 1) why the doctor thoughtspecific problems existed and 2) what the doctor prescribed for eachproblem, is desirable. It may be very time consuming to determine theanswers to these questions with current medical records

In another existing method, the doctor may divide findings, orobservations, regarding the patient into Subjective (reported by thepatient) and Objective (observed by the doctor on exam) observations.The doctor may then record in a different section an assessment of whyparticular findings caused the doctor to think that there is aparticular problem, what the probability of that problem is and thediagnosis. From there, the doctor may record plans, or actions, tohopefully remedy patients problems. This method of recording data iscommonly known as the S O A P method. The SOAP model was firstintroduced in the article titled, “Medical records that Guide and Teach”by Lawrence L. Weed, M.D. (N Engl. J. Med 1968; 278: 593-600) andrelates generally to the problem oriented medical record. Morespecifically, SOAP refers to the process of recording subjective andobjective observations, diagnosed problems or situations, and scheduledactions or treatments. Using the SOAP model, the doctor is ideallysupposed to write a SOAP note for each perceived problem in the patient.In many cases, some findings are used in the SOAP note for more than oneproblem and even more frequently plans may be performed for more thanone problem. Thus, the SOAP model inherently involves repeated doubleentry of observations, diagnoses, and actions. A system that preventsdouble entry of information is desirable.

Previous methods may use paper medical record forms that have boxes forentry of various types of data. Unfortunately, it is difficult for aservice provider to determine how much of a particular type of data willneed to be recorded, and, thus, the box may constrain the space leadingto either incomplete data collection or notes scribbled in marginsnearby or elsewhere on the form in another box.

In one prior medical record embodiment, the medical records are sourceoriented with data stored according to its source. For example, labresults may be kept together, the doctors notes may be kept together andx-ray reports may be kept together. They may all be kept in one chart,but creating a mental model of the patient at any given point in timerequires paging through the records from a specific point in time ineach of the source groupings.

SUMMARY OF CERTAIN INVENTIVE ASPECTS

The invention relates to a system and method of recording and organizingdata corresponding to an object of care. More specifically, theinvention relates to a recording system, that may be implemented on acomputer system, that organizes data corresponding to an object of care,such that each observation and action is connected to either a specificcategory of care or multiple categories of care. Throughout theapplication, a software implementation of the invention, titled‘SoapCycle’ will be described. However, the invention includes otherembodiments than those described below.

In one embodiment, the present invention relates to a data model forrecording and organizing information regarding an object of care in adatabase, the data model comprising an observation data set including aplurality of observations regarding the object of care, a category ofcare data set including a plurality of categories of care regarding theobject of care, an action data set including a plurality of actionsregarding the object of care, and a plurality of associations (which maybe graphically represented by connection lines), associating each of theplurality of categories of care to one or more of the plurality ofactions and to one or more of the plurality of observations.

In another embodiment, the present invention relates to a method ofdisplaying a medium readable by a computing system for executing acomputer process for recording and connecting data objects relating toan object of care so that the data objects are connected in a mannerthat allows a user to determine a logical relationship between aplurality of data objects by viewing the connections between theplurality of data objects. The method comprises receiving a plurality ofobservations regarding the object of care from a user controlled inputdevice, receiving a plurality of categories of care regarding the objectof care from the user controlled input device, receiving a plurality ofactions regarding the object of care from the user controlled inputdevice, receiving a plurality of entries from the user controlled inputdevice indicating one or more specific observations that are to beconnected to each specific category of care, receiving a plurality ofentries from the user controlled input device indicating one or morespecific actions that are to be connected to each specific category ofcare; storing data corresponding to the specific observations and thespecific actions that are to be connected to each specific category ofcare, and sending a GUI to an output device, the GUI including theplurality of observations, the plurality of categories of care, theplurality of actions, and a plurality of connections corresponding tothe stored data, wherein the connections are visible as solid lines.

In another embodiment, the invention relates to a data model forrecording and organizing information regarding an object of carecomprising an observation data set including a plurality ofobservations, the plurality of observations comprising a first subset ofthe plurality of observations and a second subset of the plurality ofobservations, an action data set including a plurality of actions, theplurality of actions comprising a first subset of the plurality ofactions and a second subset of the plurality of actions, a firstcategory of care connected to the first subset of the plurality ofobservations and connected to the first subset of the plurality ofactions, and a second category of care connected to the second subset ofthe plurality of observations and connected to the second subset of theplurality of actions, wherein each connection indicates a relationshipsbetween the respective connected data. In other embodiments, additionalsubsets of the plurality of observations are included and the multiplesubsets of the plurality of observations can be connected to a singlecategory of care. In other embodiments, additional subsets of theplurality of actions are included and the multiple subsets of theplurality of actions can be connected to a single category of care.

In another embodiment, the invention relates to a data model forrecording and organizing information regarding an object of carecomprising an observation data set including a plurality N observations,the plurality of observations comprising a first subset of the pluralityof observations, wherein the first subset includes a quantity from 1 toN of the plurality N observations, and a second subset of the pluralityof observations, wherein the second subset includes a quantity from 1 toN of the plurality N observation. The data model further includes anaction data set including a plurality M of actions, the plurality M ofactions comprising a first subset of the plurality M of actions, whereinthe first subset includes a quantity from 1 to M of the plurality Mactions, and a second subset of the plurality M of actions, wherein thefirst subset includes a quantity from 1 to M of the plurality M actions.The data model further comprises a first category of care connected tothe first subset of the plurality N of observations and connected to thefirst subset of the plurality M of actions, and a second category ofcare connected to the second subset of the plurality N of observationsand connected to the second subset of the plurality M of actions,wherein each connection indicates a relationship between the respectiveconnected data. In other embodiments, additional subsets of theplurality of observations are included and the multiple subsets of theplurality of observations can be connected to a single category of care.In other embodiments, additional subsets of the plurality of actions areincluded and the multiple subsets of the plurality of actions can beconnected to a single category of care.

In another embodiment, the invention relates to a system for allowingdata to be entered into a divider bar, the system comprising a GUIwindow including a divider bar dividing the GUI window into two separateportions and coupled to a database operable to store a plurality ofdata, the divider bar having a collapsed state which allows a largerarea for display of data above or below the divider bar, and an expandedstate configured to allow a user to add new data to the plurality ofdata, wherein the physical size of the expanded state is larger than thephysical size of the collapsed state. The divider bar includes a firstselectable button configured to expand the divider bar to the expandedstate when the first selectable button is selected, and a secondselectable button configured to collapse the divider bar to thecollapsed state when the second selectable button is selected.Alternatively, the divider bar includes only one button alternativelylabeled either “Expand” or “Collapse” when the bar is collapsed orexpanded, respectively. As such, the user may change the state of thedivider bar with the same button.

In another embodiment, the invention relates to a method for providingaccess to a plurality of graphic objects on a computer display. Themethod comprises (a) creating a generally rectangularly shaped graphicwindow comprising a plurality of graphic objects organized in an array,(b) creating a generally rectangularly shaped divider graphic object(“divider”) operable to separate the graphic window into two portionssuch that one or more of the plurality of graphic objects are disposedon either side of the divider, the divider comprising a collapsed stateand an expanded state, (c) enabling a user to increase the physical areaof the divider, when the divider is in the collapsed state, by changingthe divider to the expanded state; wherein, in the expanded state thedivider contains one or more of the plurality of graphic objects and isoperable to accept data input from a user controlled input device, and(d) enabling a user to decrease the physical area of the divider, whenthe divider is in the expanded state, by changing the divider to thecollapsed state; wherein, in the collapsed state the divider is notoperable to accept data input from the user controlled input device.

In another embodiment, the invention relates to a system for connectingdata objects in a GUI, comprising a plurality of text phrases divided bya plurality of text dividers, wherein each of the plurality of textphrases may be individually selected by a user, wherein when any portionof a particular text phrase is selected, the entire particular textphrase is selected, and at least one connection object, wherein any ofthe plurality of text phrases may be iteratively selected and connectedto one or more of the connection objects, wherein each of the pluralityof text phrases that are iteratively selected and connected to theconnection object are placed in a first text area disposed apart fromeach of the plurality of text phrases that are not iteratively selectedand connected to the same one or more connection objects.

In another embodiment, the invention relates to a software method forconnecting specific text objects with a connection object, the softwarereceives a plurality N of text phrases from a user controlled inputdevice, stores the plurality N of text phrases, displays in a GUI theplurality N of text phrases separated by a plurality N−1 text dividers,and iteratively receives a selection of a specific text phrase from theuser controlled input device, receives a selection of connection objectsfrom the user controlled input device, and displays a connection betweenthe selected specific text phrase and the selected connection objects.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects and features of the invention will become morefully apparent from the following description and appended claims takenin conjunction with the following drawings, where like reference numbersindicate identical or functionally similar elements.

FIG. 1 is a block diagram of a typical computer system on which thesoftware of the invention, SoapCycle, may be executed in one embodimentof the invention.

FIG. 2 is a screen shot illustrating the SoapCycle software in thestartup state in one embodiment of the invention.

FIG. 3 is a screen shot illustrating the SoapCycle software afterentering data (observations, categories, and actions), but before addingconnections between the three data types.

FIG. 4 is a screen shot illustrating the SoapCycle software after addingconnections between the three data types in one embodiment of theinvention.

FIG. 5 is a screen shot illustrating the SoapCycle software aftercompleting an entry cycle in one embodiment of the invention.

FIG. 6 is a screen shot illustrating the SoapCycle software, used in anautomobile repair context, after entering data (observations,categories, and actions), but before adding connections between thethree data types in one embodiment of the invention.

FIG. 7 is a screen shot illustrating the SoapCycle software, used in anautomobile repair context, after adding connections between the threedata types in one embodiment of the invention.

FIG. 8 is a screen shot illustrating the SoapCycle software, used in anautomobile repair context, after completing an entry cycle in oneembodiment of the invention.

FIGS. 9-12 are flowcharts illustrating the method performed by a user inorder to enter, organize, and view information stored by the SoapCyclesoftware in one embodiment of the invention.

FIG. 13 is a flowchart illustrating one embodiment of the methodperformed by the SoapCycle software.

DETAILED DESCRIPTION OF CERTAIN INVENTIVE EMBODIMENTS

The following presents a detailed description of certain specificembodiments of the invention. However, the invention can be embodied ina multitude of different ways as defined and covered by the claims. FIG.1 is a block diagram of a typical computer system on which the softwareof one embodiment of the invention, SoapCycle, may be executed. Acomputer or computing device 102 is connected to an input device 104, avisual output 106, and a network 108. The input 104 may include akeyboard, mouse, touchpad, trackball, microphone, or any other computerinput device known in the art. Visual output 106 most commonly comprisesa computer monitor, but may also be a projector, television, LCDdisplay, or any other visual output device known in the art.

The computer 102 may operate using any type of processor (e.g. Intel,AMD or Motorola), RAM, hard drive, floppy drive, video card, sound card,and other peripheral devices. Computer 102 may use any off-the-shelf orproprietary operating system, including, but not limited to: MAC OS X,UNIX, LINUX, Disk Operating System (DOS), OS/2, PalmOS, VxWorks, Windows3.X, Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP, andWindows CE. The computer 102 may be a handheld device, a cellulartelephone, or other alternative device.

In certain embodiments, network 108 may be of any topology, including,but not limited to: bus, star, or token ring topologies. The network 108may cover any amount of spatial distance, including, but not limited toa local area networks (LAN), metropolitan area networks (MAN), wide areanetworks (WAN), or the internet.

The recordation and organization software termed SoapCycle 110 issoftware that receives, records, organizes, and outputs informationrelating to objects of care. Objects of care, as discussed above, may befrom one of many service industries, including the medical andautomotive repair industries. SoapCycle 110 may execute on the computer102, receive input from input 104 and send output to visual output 106.The database 112 is written to and read from by SoapCycle 110. In otherwords, SoapCycle 110 builds the database 112 by adding data to thedatabase 112, and SoapCycle 110 may read data from the database 112 thatmay be organized, formatted, and sent to the visual output 106. FIG. 1shows the database 112 as residing on the computer 102, however, oneskilled in the art will understand that the database 112 can reside onother computers and be configured to be accessed by SoapCycle 110through methods known in the art. The database 112 may be organized andmaintained in any method known in the art.

In one embodiment, SoapCycle software is programmed in Java so that theinterface is platform independent. Following is a list of the basic dataobjects types and a list of properties associated with data object type.Only objects that represent data are listed. Those that representvarious user interface widgets are not described.

Object of Care—the Patient, Item or Object Under Care

-   -   Identification number    -   Name    -   Number of cycles—number of horizontal blocks in record    -   Number of categories—number of unique categories in record        SoapCycle User—a Simple Implementation of an Authorized User    -   Identification number    -   Name    -   Password        Observation—Data Items that Appear in the Observation Column    -   Entry identification number    -   Object of Care    -   Creation Date-Time stamp    -   Cycle number    -   User    -   Authentication—how was user authenticated, e.g. password    -   Connection set—the group of category connections    -   Observation attribute—type of observation, e.g. temperature    -   Observation value—value of observation, e.g. 98.6 F    -   Observations parameters—not used, available for modifiers        Category—Data Items that Appear in the Category Column    -   Entry identification number    -   Object of Care    -   Creation Date-Time stamp    -   Cycle number    -   User    -   Authentication—how was user authenticated, e.g. password    -   Category number—allows all fields of the category except the        number to change while maintaining a connection back to        instances of that category number historically. This allows the        user to evolve their understanding and description of a        particular category in all respects while maintaining a        historical thread back through previous descriptions.    -   Category type—e.g. problem, diagnosis, normal, prevention    -   Category value—e.g. cough, cancer, no lameness, vaccination    -   Category comment—e.g. prognosis, thoughts        Action—Data Items that Appear in the Action Column    -   Entry identification number    -   Object of Care    -   Creation Date-Time stamp    -   Planned Date-Time—when action intended, default immediate    -   Cycle number    -   User    -   Authentication—how was user authenticated, e.g. password    -   Connection set—the group of category connections    -   Invoice number—for later use with financial module    -   Quantity—e.g. number of pills, minutes of surgery    -   Charge—amount to charge customer for action    -   Action type—e.g. prescription, surgery    -   Action value—e.g. aspirin, hysterectomy    -   Action parameters—not used, available for modifiers    -   Action status—e.g. recommended, declined, done    -   Linked ?—action generates linked observations (Boolean)

Note that Observation, Category, and Action share many properties. Thisis because they share various interfaces. The cycle number and theconnection set are required within the data in order to display withinSoapCycle.

Actions and Observations have the Connection set property. Each actionand each observation keeps a list of the categories to which it isconnected. This allows the user interface to group actions orobservations together in a box when they share the same set ofconnections to categories. And it allows the interface to draw linesbetween these boxes and the categories to which they are connected.

There are some properties created for future use. Observation parameterscould be used to supply information to help interpret the observation.An example would be the normal range of a lab result. Action parametersare used for descriptive information about the action that is not aboutthe object of care. An example would be the exposure settings of anx-ray.

The ‘Linked ?’ Property of Actions is intended for future use as well.Some actions, such as a physical exam or a blood panel may generate newobservations in the next cycle. This flag would be a partial solution toproviding the user with a list of all observations resulting from aparticular action. Another connection set or similar functionality wouldbe required between each action and resulting observations.

In one embodiment, a category of care entry may be identified as one ofthree types, namely, diagnosis, preventative care, or normal care. Thecategory of care serves as a central axis, to which observations andactions are linked. As such, future observation or actions related to anexisting category of care may be linked to the existing category ofcare, eliminating the need for double entry. For example, a veterinarianmay observe a variety of conditions of a particular dog. Theseobservations may come both from the owner telling the veterinarian aboutthe dog's conditions and the veterinarian making observations once thedog is in his sight. These observations may lead to a plurality ofcategories of care, for example: normal, diarrhea—severe, and pinchednerve. Each of these three categories of care may be linked to aplurality of observations that led the veterinarian to that particularcategory of care. For example, the observations ‘no stiffness’ and ‘novomiting’ may be linked to a normal category of care while theobservations ‘owner reports diarrhea 6 times per day’ and ‘lack ofenergy’ may be linked to the ‘diarrhea—severe’ category of care. Inaddition, according to the invention, each of the actions taken islinked directly to the category of care for which it attempts to remedy.In this way, any future reader may easily ascertain the observationsthat led the veterinarian to a certain category of care, and further,the actions that were taken to remedy the category of care.

The invention also allows users of an already existing object file toadd observations and actions which may be linked to already existingcategories of care. Continuing with the veterinarian example above, on afuture visit by the same dog the veterinarian may observe additionalconditions that imply that the dog has a pinched nerve. Theseobservations may be recorded and linked to the pre-existing category ofcare ‘pinched nerve,’ such that the veterinarian need not re-enter thepre-existing category of care. Furthermore the veterinarian may recordadditional actions taken to remedy a pre-existing category of care andlink the actions to the pre-existing category of care.

According to the invention, all data related to a patient or object ofcare is integrated in to one view. For example, the results of thephysical exam, x-ray findings, prescriptions, lab results, and financialcharges are not separated in to different windows or tabs so that theyall may be viewed together, providing more context and therefore richermeaning to the reader.

FIG. 2 is a screen shot illustrating one embodiment of the SoapCyclesoftware in the startup state 200. FIGS. 2 through 5 illustrate aversion of SoapCycle that has been adapted for use in a medical orveterinarian practice while FIGS. 6 through 8 illustrate a version ofSoapCycle that has been adapted for use in an automobile repair company.While these two specific applications of SoapCycle are discussed indetail herein, it is contemplated that the invention may be used by anyindustry that may keep problem solving records relating to specificobjects. For example, the SoapCycle software may be used by a schooladministration office to keep discipline records for each student, atechnical support department may keep records of each of their callers,and a prison may keep records of each inmate. One of ordinary skill inthe art may easily adapt the examples explained in the DetailedDescription to any other problem solving environment.

The SoapCycle Graphic User Interface (“GUI”) is divided generally in tothree columns titled observations 202, categories 204, and actions 206.The name of the operator is shown in the user field 208 and the name ofthe patient is shown in the patient field 210. In one embodiment, theoperator must log on, by entering a login name and password, beforeselecting an existing patient record or creating a new patient record.In another embodiment, the startup state 200 may also show additionalpatient information, such as species, date of birth, age, sex, breed,coloring, the owners name, and other biographical and billinginformation corresponding to the owner. These patient information fieldsmay vary depending on the veterinarians preferences and may be easilymodified by the veterinarian. Patient information fields may genericallybe referred to as Object Information Fields which may include, forexample, client information fields, customer information fields, orinmate information fields in other service industries. For example, inan embodiment of SoapCycle adapted to computer technical supportrecords, the object information fields may include customer name,address, telephone number, type of computer, and computer knowledge.

The observations column 202 may be used to enter and displayobservations by the service provider (i.e. the user) regarding theobject of care (e.g., an animal in a veterinarian settings or anautomobile in a mechanical setting). In the medical field, observationshave traditionally been divided into Subjective (S) and Objective (O)observations. Subjective observations refer to information reported bythe patient and objective observations refer to information collected bythe doctor. In the preferred embodiment, the subjective and objectiveobservations are both recorded in the observations column 202. Becausethe subjective or objective nature of the data is almost alwaysimplicitly obvious (e.g. patient reports coughing for two months versespatient had deep cough during examination), combining all observationsin to one column simplifies the record.

The categories column 204 may be used to enter and display thecategories of care (“categories”), such as normal, diagnosis, orpreventative care. The categories are the central organizing axis of therecord. After the service provider notes the pertinent observations, anassessment discussing what the observations meant, whether theyindicated new problems, or the prognosis may be recorded as a categoryof care. There may be categories of care that are not necessarilyproblems, such as preventive or normal care. According to the invention,categories may be added as needed by the specific service provider. Manyin the medical field like to distinguish between problems and diagnoses(e.g. cough is a problem, lung cancer is a diagnosis). SoapCycle allowssuch medical practitioners to create separate categories for problemsand diagnoses. Other service industries may also create and usedifferent categories of care.

The actions column 206 may be used to enter and display any actionstaken or prescribed, such as x-rays, lab tests, prescriptions, orspecial instructions. Actions are derived from the plans (P) element ofthe SOAP model. The actions column 206 may include specific actioninformation that is not specific to the object of care. For example,when taking x-rays, the exposure settings would belong in this column,but any abnormalities found in the x-ray would go in the observationscolumn.

The cycle work area 240 displays all observations, categories, andactions recorded in the current cycle. A cycle is a group ofobservations, categories and actions.

FIG. 3 is a screen shot illustrating one embodiment of the SoapCyclesoftware after entering data (observations, categories, and actions),but before adding connections between the three data types. Asobservations, categories, and actions are added to the patient record,they are listed in the cycle work area 240. For example, an observationis entered in the observation entry block 312 using any combination ofpull-down menus and text entry fields. In the embodiment shown in FIG.3, the observation entry block includes a pull down menu 322 and a textentry field 332. In one embodiment, common observations may bepre-stored in pull-down menu 322 so that the user may quickly selectthem. The user may also enter other observations, or more detailsregarding an observation selected in the pull down menu 322, in the textentry field 332. In another embodiment, the operator may addobservations to the existing list contained in the pull-down menu 322.It is contemplated that any data entry method known in the art may beused to enter observations in the observation entry block 312. When theuser is done entering the observation in the observation entry block312, the user may click the enter button 342 or push an enter or returnkey to transfer the current observation to the current cycle work area240. Each entered observation in a single cycle will initially be placedin a single textlist box 302, separated by semicolons. Thus, each groupof text in between semicolons in textlist box 302 is a separatelyentered observation. For example, in FIG. 3 the user has entered 9separate observations, namely ‘vomiting—3 times a day for 3 days’,‘Diarrhea—once a week always with grass in it’, ‘Ate fat trimmings fromdinner 3 nights ago’, ‘No coughing, ‘No sneezing’, ‘No pruritis’,‘Stiffness—occasionally in the morning during the winter’, ‘Noseizures’, and ‘No polyphagia.’ The SoapCycle software may store a time,date, name of user that entered, and authentication method of user thatentered (e.g. password authentication) associated with each individualobservation, category, and action, which may be visible in a pop-up textbox when the pointer is placed over the top of the observation. The 9separate observations of FIG. 3 are displayed as free text (i.e. not ina list format, but in paragraph format) so that the amount of spacerequired in the GUI may be reduced. For example, if the observationswere displayed in a standard list, 9 text lines would be required todisplay all 9 observations. In addition, although the observations aredisplayed as free text divided by commas (or any other text divider inother embodiments), each observation may be individually selected (i.e.without selecting an entire row of text) and associated with either aspecific category or to multiple categories (discussed below with regardto FIG. 4).

In a similar way as discussed above, categories and actions are entered.Categories may be selected from various pull down menus such as acategory type pull down menu 324A, a category title pull down menu 324Band a category number pull down menu 324C. A list of categories in thepull-down menus 324A-C, which allows new categories to be added, andcomments may be made in the comment box 334. When a category has beenselected or entered, the category may be transferred to the currentcycle work area 240 by clicking on the enter button 344 or by pushing areturn or enter key. Each category entered will be placed in a separatecategory box 304. The user may enter actions in a similar fashion, byselecting actions from pull-down menus 326A and 326B and/or enteringcomments in a comment box 336. The pull down menu 326A is for actiongroups and the pull down menu 326B is for actions. Making a selection inthe menu 326A selects a subset of available actions to be displayed inthe menu 326B. Actions may also include a flat billing rate, or,alternatively, a billing time and rate for each individual action. Forexample, the action of performing a chest x-ray may have a flat billingrate of $70, while the action of performing a surgery may include anhourly billing rate which may be calculated by the SoapCycle softwareusing an entered billing time and rate. When actions are entered (byclicking the actions enter button 346 or by pushing a return or enterkey), they are initially placed in a single actions box 306 divided byhorizontal lines (or any other dividing means). Like the individualobservations, each individual action may be separately selected andlinked to at least one category box 304.

FIG. 4 is a screen shot illustrating one embodiment of the SoapCyclesoftware after adding connections between the three data types. Althoughconnections may be created in a variety of different methods, one methodwill be described hereafter. Each separate observation (i.e. each phrasebetween semicolons) may be selected by clicking on the phrase. Once aspecific phrase is selected the text of that specific phrase may behighlighted. The user may then highlights the category (by clicking onit) which the already selected observation is to be connected to. Theconnection is made when the Add Connections button 410 is clicked theGUI displays a straight line between the two connected objects. Eachremaining observation may likewise be selected and connected to aspecific category in the same manner. As each connection is beingcreated the SoapCycle software creates new observation boxes 302 asnecessary. In addition, multiple connections may be createdsimultaneously by selecting multiple observations and one or morecategories before clicking the Add connections button 410. For example,the connection between the observation box 302A and the category box304A may be created by the user clicking on “No coughing”, “Nosneezing”, “No pruritis”, “No seizures”, and “No polyphagia” in theobservations column 202 (FIG. 3), clicking on “Normal” in the categoriescolumn 204, and then clicking the Add Connections button 410.

In the embodiment of FIG. 4, individual observation boxes 302 containobservations connected to a specific category. As the user connectsmultiple observation boxes to a single category box, the multipleobservation boxes are consolidated into a single box. FIG. 4 illustratesthree observation boxes 302A, 302B, and 302C that have been created as aresult of the connections chosen by the user. For example, the threeobservations ‘vomiting—3 times a day for 3 days’, ‘Diarrhea—once a weekalways with grass in it’, and ‘Ate fat trimmings from dinner 3 nightsago’ were all connected with the category pancreatitis 304B, and thusall three observations are included in a single observation box 302B,and are connected to the category box 304B with a single connectionline. In addition, a specific observation may be connected to multiplecategories. If a specific observation is connected to multiplecategories, the observation can be listed in an observation box 302 withline connections to the multiple categories. If additional observationsshare identical connections (i.e. to multiple categories), theobservations can share the same observation box 302. Connections betweenthe categories and actions are created in a similar manner. The userclicks on a category, the category is highlighted, the desired actionfor that category is selected (by clicking on it), and the Addconnections 410 button is clicked creating a connection. Each categorymay have zero, one, or any plurality of actions connected to it. In theexample of FIG. 4, the normal category 304A has zero actions connectedto it, the pancreatitis category 304B has four actions connected to it,and the arthritis category has zero actions connected to it.Additionally, connections between a specific category, multipleobservations, and multiple actions may be created simultaneously byselecting the specific category, along with all observations and actionsto be connected to the specific category, and then clicking the AddConnections 410 button.

The Replace Connections button 420 will remove any existing connectionsattached to the selected observations, category, and actions and createnew connections between the selected observations, category, andactions. In other words the Replace Connections button 420 removesconnections currently attached to the selected observations or actionsand creates new connections between the selected category, observations,and actions.

After all of the connections are made a reader may easily determine thespecific observations that led to each specific category of care, and,in addition, what actions were performed or prescribed for each specificcategory of care.

FIG. 5 is a screen shot illustrating one embodiment of the SoapCyclesoftware after completing an entry cycle. When each observation andaction is connected to a category the current cycle is complete. Theuser may then move the current cycle from the current cycle work area toa cycle history area 510. The entry area 235 (FIG. 2) has beencollapsed, hiding the entry area 235, and making visible the cyclehistory area 510. The cycle history area can be made visible withoutcollapsing the entry area by dragging the divider bar entry area down.In other words, the divider bar motions are available whether thedivider bar is expanded or collapsed. The entry bar 520 may be movedvertically to any location on the GUI by clicking and dragging it, orthe entry bar 520 may quickly be moved to the top or bottom of the GUIby clicking the send to top button 504 or the send to bottom button 506,respectively. The entry area 235 may be expanded (allowing further dataentry) by clicking on the expand button 502. The user may create a newcycle by clicking the New Cycle button 430.

The screen shot shown in FIG. 5, with the entry area 235 collapsed, maybe used primarily to review records already stored in the database. Forexample, when a patient returns for a follow-up visit the cycle historyarea 510 provides a quick review of observations, categories, andactions, and more importantly provides the observation and actionconnections corresponding with each individual category. In anotherembodiment, the user can drag entries from the cycle history area intothe cycle work area to create new entries. This would save the user fromfilling out a form. For example, a patient may have some of the sameobservations as on a previous visit, the patient may have the samecategory of care as on a previous visit, or the user may wish to repeatan action from a previous visit, e.g., refill a prescription.

FIGS. 6-8 show the SoapCycle software used in an automotive repairsetting. The object of care is now an automobile, and the observations,categories of care, and actions are all related to the automobile. Theobservations 302 in FIGS. 6-8 include subjective and objectiveobservations specific to the Volvo object of care 210. Observationsinclude, among others, ‘compression tests normal all cylinders,’‘maintenance free battery hydrometer window green,’ and ‘Fuel filterclean.’ The categories column 204 may be used to enter and display thecategories of care, such as preventative, normal, bad ignition switch,clogged fuel filter, etc. As with the veterinarian example of FIGS. 3-5,the categories are the central organizing axis of the record. Theactions column 206 may be used to enter and display any actions taken orprescribed, such as new ignition switch, new fuel filter, and laborassociated with any services performed.

FIG. 6 is a screen shot illustrating one embodiment of the SoapCyclesoftware after entering data (observations, categories, and actions),but before adding connections between the three data types. As shown inFIG. 6, several observations 302, categories 304, and actions 306related to the Volvo object of care 210 have been entered in to thecurrent cycle. The data is entered into the SoapCycle interface in amanner similar to that described with respect to FIG. 3.

FIG. 7 is a screen shot illustrating one embodiment of the SoapCyclesoftware after adding connections between the three data types. Forexample, FIG. 7 illustrates that observation 302 d ‘Ignition switchtests at 0 volts,’ category 304 d ‘bad ignition switch,’ and action 306d ‘New ignition switch #1 and Labor replace ignition switch #1.25’ havebeen connected by the connecting lines 440. The connections are made ina manner similar to that described with respect to FIG. 4.

FIG. 8 is a screen shot illustrating one embodiment of the SoapCyclesoftware after completing an entry cycle. When each observation andaction is connected to a category the current cycle is complete. For adetailed explanation of the process of completing an entry cycle, seeFIG. 4.

As can be seen from the preceding examples, the SoapCycle software maybe adapted to track an object of care in many different industries. Theveterinarian (FIGS. 3-5) and automotive (FIGS. 6-8) examples illustratethe application of SoapCycle to two specific industries. These examplesare not intended to limit the use of the SoapCycle software, but toillustrate the broad range of uses that are possible. It is contemplatedthat SoapCycle may be used in a similar manner to record observations,categories, and actions relating to an object of care in any otherindustry.

FIG. 9 is a flowchart illustrating one embodiment of the processperformed by a SoapCycle user in operating the software. Certain blocksof FIG. 9 (blocks 1002, 1102, and 1202) have been expanded in FIGS.10-12 in order to more fully illustrate certain aspects of theinvention.

In block 902 the user logs in to the SoapCycle software. In oneembodiment, each user has a unique login ID and password. In anotherembodiment, groups of users share a common login ID and password.

In block 904 the user selects the object of care that they want toenter/view data concerning. As stated above, an object of care may be apatient, client, customer, automobile, student, or any other object,whether living or inanimate.

In block 906 the SoapCycle main record window appears. The main recordwindow displays information regarding the selected object of care 210and allows entry of additional information. At this point the user maychoose either to enter new data 1002 or review previous records 910.

In block 918, the user chooses whether or not to review a record. If theuser decides to review a record, in block 910, the user reviews theprevious record. In block 912 the user clicks the Enter bar and uses thecollapse and down arrow buttons to maximize space for viewing theprevious record in the top pane. In block 914 the user uses the scrollbar to scroll up and down through the record.

In block 920, the user chooses whether or not to enter new data. If theuser decides to enter new data, the method proceeds through blocks 1002,1102, and 1202, represented in FIGS. 10, 11, and 12, respectively. Inbrief, block 1002 allows the entry of new data, including categories ofcare, observations, and actions. In block 1102, the user createsassociations between the entered data which are displayed as connectionlines in the GUI. In block 1202, the newly entered data and associationsare stored according to the storage configuration employed by theparticular user.

After the user has completed a new data entry cycle (i.e. blocks 1002,1102, and 1202) and/or a review record cycle (i.e. blocks 910, 912, and914) the GUI display is updated and the user is presented with a seriesof decision blocks. More specifically, in block 916, the GUI display isupdated to include any of the new data entered or changed during eitheran entry or review cycle. While the GUI update is illustrated at aspecific location in the flowchart of FIG. 9, it is contemplated thatthe GUI is updates continuously as the user interacts with the SoapCyclesoftware.

In block 922 the user decides whether to quit (i.e. exit) the SoapCyclesoftware or continue viewing the main record window. If the user decidesto quit, the SoapCycle software will be closed in block 924 and the userwill need to Login (block 902) in order to again access the SoapCycledatabase. Alternatively, if the user does not elect to quit, the processreturns to block 906 where the main record window is displayed. In oneembodiment, the process, by default, flows from block 922 to step 906without any input from the user until the user indicates a desire toquit. In other words, the user only exits the SoapCycle software bypressing a Quit or Exit button so that the process of FIG. 9 isrepeated, without user input in block 922, until the Quit or Exit buttonis selected.

FIG. 10 is a flowchart illustrating one embodiment of the process ofentering new data using the SoapCycle interface. FIG. 10 is an expandedversion of block 1002 (FIG. 9), labeled Enter New Data.

In block 1004, if the entry bar is collapsed, the user clicks on theEntry Bar Expand button 502 (FIG. 5) to reveal entry forms.

In block 1006, if the entry bar is not at the top, the user clicks theEntry Bar Up arrow button to maximize space for display of currententries.

In block 1008, the user chooses either an observation (left), category(middle) or action (right) entry form. A specific entry form is selectedby either clicking on the top field of form, or if the user is alreadyin the entry form, Tabbing to the last field and then Control-Tabbing tothe top of the next form.

In block 1010, the user tabs through the fields within an entry form,entering text in each field until an entry is completed.

In block 1012 the user puts the entry into the current cycle of therecord (appearing in the bottom pane below the entry bar) by 1) pushingthe return key, 2) pushing the enter key, or 3) clicking the enterbutton below the form. This will also return the user to the top fieldof the form he is using. At this point the user may either chooseanother observation, category or action entry form (block 1008) orcontinue to block 1102 to create data connections.

FIG. 11 is a flowchart illustrating one embodiment of the process ofcreating data connections using the SoapCycle interface. FIG. 11 is anexpanded version of block 1102 (FIG. 9), labeled Create DataConnections. In block 1104, the user makes sure that the bottom panecontaining the current cycle is visible by clicking the Entry Bar Uparrow button if needed. The bottom pane must have at least one entry inthe middle column and at least one entry in either the right or leftcolumn. If not, the user returns to block 1002 and enters the datafirst.

In block 1106 the user clicks on all categories to which he wishes toconnect a group of observations and/or actions. When he clicks on acategory, it will be highlighted showing it is selected. If the userwishes to deselect a category, he clicks on it again. At this point theuser has two options: (1) In block 1108 the user returns to block 1002(FIG. 10) and enters additional observations or actions. The newobservations or actions will automatically be grouped in a box withlines connected to the currently selected categories, or (2) addingadditional connections by proceeding to block 1110.

In block 1110, the user clicks on each observation and each action hewishes to connect to the currently selected categories, highlighting theselected observations and actions. An item may be deselected by clickingon it again. At this point the user must choose either to replaceexisting connections (block 1112) or add new connection (block 1114)

In block 1112, the user clicks the Replace Connections button. Currentlyselected observations and actions will be grouped in a left column boxand a right column box respectively with lines connected to thecurrently selected categories.

In block 1114, the user clicks the Add Connections button. Currentlyselected observations and actions will have currently selectedcategories added to their set of connections. They will then be groupedin boxes with observations or actions that share their set ofconnections.

After either block 1112 or 1114 is completed the user continues to block1202 where the completed cycle is stored.

FIG. 12 is a flowchart illustrating one embodiment of the process ofstoring a completed cycle using the SoapCycle interface. FIG. 12 is anexpanded version of block 1202 (FIG. 9), labeled Store Completed Cycle.In block 1204, if a cycle of data (in the bottom pane) is particularlylarge, the user may wish to minimize scrolling and free more space forcreating connections or viewing the data before storage. To do this, theuser clicks on the Entry Bar: Collapse button and the Entry Bar Up arrowbutton.

In block 1206, the user clicks on the New Cycle button. This will attachthe current cycle from the bottom pane to the bottom of the previousrecord in the top pane and clear the bottom pane for new data entry. Atthis point, the user may choose to review previous records 910, enternew data 1002 or quit 1212.

As indicated above, FIGS. 9-12 illustrate one embodiment of the processperformed by a SoapCycle user in operating the software with respect toany object of care. Similarly, FIG. 13 is a flowchart illustrating oneembodiment of the method performed by the SoapCycle software withrespect to a particular object of care. As the process of FIG. 13 isperformed, the software is periodically storing received information inmemory, recording information in non-volatile memory, and/or storinginformation on a permanent storage medium according to any of a varietyof known storage technique known in the programming art.

After a specific object of care has been selected (either by selectingan existing object of care or adding a new object of care), in block1302, the software receives a plurality of observations regarding theobject of care. In one embodiment the observations are entered using akeyboard connected to the computer running the SoapCycle software.However, it is contemplated that any of a variety of other known inputdevice, such as a mouse, touchpad, or microphone, may be used to enterobservations.

In block 1304, the software receives a plurality of categories of care.Again, the categories of care may be received by the software from aninput device connected to the computer.

In block 1306, the software receives a plurality of actions meant forthe object of care.

In block 1308, the software receives a plurality of associations betweena particular category of care and one or more observations. Inparticular, after the user selects a specific category of care, thesoftware receives the selection and may indicate the selection in theGUI by emphasizing, e.g., underlining or shading the selected categoryof care, for example. An association between the currently selectedcategory of care and an observation is then stored by the software asthe user selects a particular observation and clicks on the AddConnections button. If the particular category of care is stillselected, or the user re-selects the same category of care, moreobservations may be associated with the particular category of care. Inone embodiment, when more than one observation is associated with aparticular category of care, the software displays the multipleobservations in the GUI as a group. For example, the group 302A in FIG.4 comprises five separate observations that were each associated withthe category of care 304A. In another embodiment, the user may select aparticular category of care and multiple observations before clicking onthe Add connections button, thus resulting in substantially identicalgrouping in the GUI.

In block 1308, the software also receives a plurality of associationsbetween a particular category of care and one or more actions. Theselection and storage of associations between a category of care andactions is performed in a similar manner as discussed immediately abovewith respect to the observations. Likewise, the grouping of all actionsassociated with a particular category of care is automatically performedby the software.

In one embodiment, the software is capable of receiving data in blocks1302, 1304, 1306, and 1308 in other sequences. For example, the softwaremay receive, in temporal sequence, a category of care in block 1304,multiple observations in block 1302, an action in block 1306, anotherobservation in block 1302, and then an association in block 1308.

In block 1310, the software stores received information in memory,records information in non-volatile memory, and/or writes information ona permanent storage medium. As mentioned above, block 1310 may operateto store information periodically throughout the process of FIG. 13. Inone embodiment, the software may store information received from blocks1302, 1304, 1306 and 1308 immediately after the information is receivedby the software. Occasionally, as indicated by the circumstances of theimplementation, batches of the received data are accumulated in memorybefore they are stored in the main database (on a hard drive or networkserver, for example). The storage of batches of data may be advantageouswhen using a mobile data collection unit that is prone to disconnectionfrom the main database or for reasons of efficiency and speed, such as aslow database connection. If problems are encountered storing a batch ofdata, the database may return a message indicating such and allowing theuser to try again. In this embodiment, the database stores additionaldata relating to the status of synchronization between the twodatastores.

In block 1312, the GUI is updated as soon as the software receives thedata. In an advantageous embodiment, the software updates the GUI withinformation as soon as it is received. For example, after the softwarereceives a new observation from the user controlled input device, theGUI is immediately updated to show the new observation.

Specific parts, shapes, materials, functions and modules have been setforth, herein. However, a skilled technologist will realize that thereare many ways to fabricate the system of the present invention, and thatthere are many parts, components, modules or functions that may besubstituted for those listed above. While the above detailed descriptionhas shown, described, and pointed out the fundamental novel features ofthe invention as applied to various embodiments, it will be understoodthat various omissions and substitutions and changes in the form anddetails of the components illustrated may be made by those skilled inthe art, without departing from the spirit or essential characteristicsof the invention.

1. A user interface for receiving and displaying information regardingan object of care, the user interface comprising: an observation panefor displaying a plurality of observations regarding said object ofcare, a category of care pane for displaying a plurality of categoriesof care regarding said object of care, an action pane for displaying aplurality of actions regarding said object of care, wherein theobservation pane, category of care pane, and action pane areconcurrently displayed in the user interface, a plurality of visuallyperceptible associations comprising at least a first associationassociating a first of said plurality of categories of care displayed inthe category of care pane to one or more of said plurality ofobservations displayed in the observation pane, and a second associationassociating a second of said plurality of categories of care displayedin the category of care pane to one or more of said plurality of actionsdisplayed in the action pane.
 2. The user interface of claim 1, whereinsaid observation data set, said category of care data set, and saidaction data set are textually displayed in a Graphical User Interface(“GUI”).
 3. The user interface of claim 2, wherein said observation dataset comprises a plurality of text phrases divided by a plurality of textdividers such that more than one of said text phrases may be displayedon a single display line of said GUI with only said text dividersseparating said more than one of said text phrases, wherein each of saidplurality of text phrases may be individually selected by a user withoutselecting the entire said single display line of said GUI, wherein whenany portion of a particular text phrase is selected, the entireparticular text phrase is automatically selected.
 4. The user interfaceof claim 2, wherein said action data set comprises a plurality of textphrases divided by a plurality of text dividers such that more than oneof said text phrases may be displayed on a single display line of saidGUI with only said text dividers separating said more than one of saidtext phrases, wherein each of said plurality of text phrases may beindividually selected by a user without selecting the entire said singledisplay line of said GUI, wherein when any portion of a particular textphrase is selected, the entire particular text phrase is automaticallyselected.
 5. The user interface of claim 1, wherein said plurality ofassociations are visible in the GUI as solid lines.
 6. The userinterface of claim 5, wherein said GUI includes: an observation columnoperable to display said observation data set; an action column operableto display said action data set; and a category of care column disposedbetween said observation column and said action column operable todisplay said category of care data set.
 7. The user interface of claim1, wherein each of said plurality of observations associated with aparticular category of care is automatically placed in an observationgroup, which is a portion of said observation data set.
 8. The userinterface of claim 1, wherein said object of care is a patient in amedical practice.
 9. The user interface of claim 1, wherein said objectof care is an animal in a veterinarian practice.
 10. The user interfaceof claim 1, wherein said object of care is an automobile.
 11. The userinterface of claim 1, wherein said observation data set, said categoryof care data set, and said action data set are concurrently displayed inthe user interface.
 12. The user interface of claim 11, wherein thecategory of care data set is configured to receive additional categoriesof care via the user interface, wherein the user interface comprises atext entry area for receiving the additional categories of care, thetext area being concurrently displayed with the observation data set,the category of care data set, and the action data set.
 13. The userinterface of claim 11, wherein the associations between the plurality ofcategories of care and the observations are visible as solid lines inthe user interface.
 14. The user interface of claim 1, wherein saidobservation data set is displayed in a first column of a user interface,said category of care data set is displayed in a second column of saiduser interface, and said action data set is displayed in a third columnof said user interface.
 15. The user interface of claim 1, wherein atleast one of the observations indicates an abnormal characteristic ofthe object of care and at least one of the observations indicates anormal characteristic of the object of care, at least one of theassociations associating the normal characteristic with the normalcategory of care.
 16. The user interface of claim 1, wherein saidobservation data set comprises a plurality of text phrases divided by aplurality of text dividers such that more than one of said text phrasesare displayed on a single display line of said user interface with onlysaid text dividers separating said more than one of said text phrases.17. The user interface of claim 1, wherein said observation data setcomprises a plurality of text phrases divided by a plurality of textdividers such that at least one of said text phrases is displayed onmultiple display lines of said user interface.
 18. The user interface ofclaim 1, wherein said user interface displays each of said observationsassociated with a particular category of care in a bounded area separatefrom observations that are not associated with the particular categoryof care.
 19. The user interface of claim 1, wherein said user interfacedisplays each of said observations associated with a particular group ofcategories of care in a bounded area separate from observations that arenot associated with each of the categories of care in the particulargroup.
 20. The user interface of claim 1, wherein said observation dataset is displayed in a first column of the output device, said categoryof care data set is displayed in a second column of the output device,and said action data set is displayed in a third column of the outputdevice.
 21. The user interface of claim 1, wherein the first associationassociates the first of said plurality of categories of care displayedin the category of care pane to more than one of said plurality ofobservations displayed in the observation pane, and the secondassociation associates the second of said plurality of categories ofcare displayed in the category of care pane to more than one of saidplurality of actions displayed in the action pane.
 22. A method ofrecording and associating data objects relating to an object of care sothat the data objects are associated in a manner that allows a user todetermine a logical relationship between a plurality of data objects byviewing connections indicative of associations between the plurality ofdata objects, said method comprising: receiving a plurality ofobservations regarding said object of care from a user controlled inputdevice, receiving a plurality of categories of care regarding saidobject of care from said user controlled input device, receiving aplurality of actions regarding said object of care from said usercontrolled input device; receiving a plurality of entries from said usercontrolled input device indicating one or more specific observationsthat are to be associated with each specific category of care; receivinga plurality of entries from said user controlled input device indicatingone or more specific actions that are to be associated with eachspecific category of care; storing data corresponding to said specificobservations and said specific actions that are to be associated to eachspecific category of care; concurrently displaying on an output devicethe plurality of observations, the plurality of categories of care, theplurality of actions, and a plurality of associations corresponding tosaid stored data, wherein said associations are visible as solid lines.23. The method of claim 22, further comprising: grouping each of saidplurality of observations associated with a particular category of careso as to create an observation group.
 24. The method of claim 23,wherein said graphical information includes said observation group. 25.The method of claim 22, further comprising: grouping each of saidplurality of actions associated with a particular category of care so asto create an action group.
 26. The method of claim 25, wherein said eachof said plurality of actions associated with a particular category ofcare are displayed as a group in said graphical information.
 27. Asystem for recording and organizing information regarding an object ofcare comprising: an observation data set including a plurality ofobservations, said plurality of observations comprising a first subsetof said plurality of observations and a second subset of said pluralityof observations; an action data set including a plurality of actions,said plurality of actions comprising a first subset of said plurality ofactions and a second subset of said plurality of actions; a firstcategory of care connected to said first subset of said plurality ofobservations and connected to said first subset of said plurality ofactions; a second category of care connected to said second subset ofsaid plurality of observations and connected to said second subset ofsaid plurality of actions, and a user interface concurrently displayingsaid observation data set, said first and second categories of care, andsaid action data set.
 28. The system of claim 27, wherein saidobservation data set comprises a third subset of said plurality ofobservations and said action data set includes a third subset of saidplurality of actions, said data model comprising: a third category ofcare connected to said third subset of said plurality of observationsand connected to said third subset of said plurality of actions.
 29. Asystem for recording and organizing information regarding an object ofcare comprising: an observation data set including a plurality Nobservations, said plurality of observations comprising a first subsetof said plurality of observations, wherein said first subset includes aquantity from 1 to N of said plurality N observations; and a secondsubset of said plurality of observations, wherein said second subsetincludes a quantity from 1 to N of said plurality N observations; anaction data set including a plurality M of actions, said plurality M ofactions comprising a first subset of said plurality M of actions,wherein said first subset includes a quantity from 1 to M of saidplurality M actions; and a second subset of said plurality M of actions,wherein said first subset includes a quantity from 1 to M of saidplurality M actions; a first category of care connected to said firstsubset of said plurality N of observations and connected to said firstsubset of said plurality M of actions; a second category of careconnected to said second subset of said plurality N of observations andconnected to said second subset of said plurality M of actions; and auser interface concurrently displaying said observation data set, saidfirst and second categories of care, and said action data set.
 30. Asystem for connecting data objects in a user interface, comprising: auser interface concurrently displaying a plurality of observations, aplurality of categories of care, and a plurality of actions associatedwith an object of care; a plurality of text phrases concurrentlydisplayed in the user interface, the text phrases being divided by aplurality of text dividers, wherein each of said plurality of textphrases may be individually selected by a user, wherein when any portionof a particular text phrase is selected, the entire particular textphrase is selected; and a connection object; wherein any of saidplurality of text phrases may be iteratively selected and connected tosaid connection object, wherein each of said plurality of text phrasesthat are iteratively selected and connected to said connection objectare automatically displayed in a bounded area of the user interface,wherein said plurality of text phrases that are not iteratively selectedand connected to said connection object are concurrently displayed inthe user interface outside of the bounded area.
 31. The system of claim30 further comprising: a second connection object; wherein any of saidplurality of text phrases may be iteratively selected and connected tosaid second connection object, wherein each of said plurality of textphrases that are iteratively selected and connected to said secondconnection object are automatically placed in a second bounded area onthe display, wherein said plurality of text phrases that are notiteratively selected and connected to said second connection object areconcurrently displayed in the user interface outside of the secondbounded area.
 32. The system of claim 30, wherein said connection objectis a category of care.
 33. The system of claim 32, wherein saidplurality of text phrases represent a plurality of observationsregarding an object of care.
 34. The system of claim 32, wherein saidplurality of text phrases represent a plurality of actions regarding anobject of care.
 35. The system of claim 30 wherein at least one of thetext phrases comprises a first and second portion, the first portionbeing displayed on a first line of a display device and the secondportion being displayed on a second line of the display device.
 36. Acomputer readable medium including software for executing the method ofconnecting specific text objects with a connection object, said methodcomprising: concurrently displaying on an output device a plurality ofobservations, a category of care, a plurality of actions, and one ormore associations depicting associations between selected of the actionsand the category of care; receiving a plurality N of text phrases from auser controlled input device; storing said plurality N of text phrases;displaying in a bounded area of a user interface said plurality N oftext phrases separated by a plurality N−1 text dividers, whereinportions of two or more of the text phrases are displayed on a singleline within the bounded area; iteratively performing the following:receiving a selection of a specific text phrase from said usercontrolled input device; receiving a selection of a connection objectfrom said user controlled input device, said connection object beingconcurrently displayed outside of the bounded area in the userinterface; displaying a line between said selected specific text phrasewithin the bounded area and said selected connection object outside ofthe bounded area.
 37. The computer readable medium of claim 36, whereineach of said selected specific text phrases associated with a specificconnection object is disposed in a text area separate from all othersaid text phrases.
 38. The computer readable medium of claim 36, whereinsaid connection object is a category of care.
 39. The computer readablemedium of claim 36, wherein said plurality N of text phrases represent aplurality of observations regarding an object of care.
 40. The computerreadable medium of claim 36, wherein said plurality N of text phrasesrepresent a plurality of actions regarding an object of care.
 41. Thecomputer readable medium of claim 36, wherein said plurality N of textphrases represent a plurality of actions and a plurality of observationsregarding an object of care.